Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1259

reference
486-tree-1
name
1259
tree-preservation-order

undefined

486-tpo-1
uprn
address-text
point
POINT (-1.023561 50.882991)
geometry
MULTIPOLYGON (((-1.023505 50.882985,-1.023507 50.882996,-1.023515 50.883007,-1.023528 50.883015,-1.023543 50.883020,-1.023561 50.883022,-1.023578 50.883020,-1.023594 50.883015,-1.023607 50.883007,-1.023615 50.882997,-1.023618 50.882986,-1.023616 50.882975,-1.023608 50.882965,-1.023596 50.882957,-1.023580 50.882952,-1.023562 50.882950,-1.023545 50.882951,-1.023529 50.882956,-1.023516 50.882964,-1.023508 50.882974,-1.023505 50.882985)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL